Remove unsafe from some vision framework functions #675
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is far from comprehensive but is all of the functions that I am currently using from vision framework.
I tried following the guide in the README - none of these functions have any meaningful limitations on their parameters.
The only point that I am unsure of is the last one:
I would really like to add the function
VNImageRequestHandler::performRequests_erroras a safe function as well. It can throw an exception if it gets invalid parameters, but the rust function returns aResult<(), Retained<NSError>>so I'm not sure why it should be considered unsafe.Either way - I couldn't get header-translator to generate a version of the function marked safe - tried with
class.VNImageRequestHandler.methods."performRequests:error:_".unsafe = falsebut it didn't work (possibly due to the underscore)